Architecture of GCB for Service Mesh and HTTPS/2 Support with Metadata
The following diagram illustrates the architecture of Gigamon Containerized Broker for service mesh and HTTPS/2 support with metadata environment.
- The GCB Controller is registered with GigaVUE-FM and the traffic policy is deployed on the GCBs.
- Communication of configuration, data, and statistics to and from GCB is performed through the GCB Controller Service. GigaVUE-FM communicates with the GCB Pods through the GCB Controller.
- Each GCB Pod is registered with GigaVUE-FM and the traffic policy is deployed on the GCBs.
- The Pcapper collects the network traffic and sends the HTTP packets to GCB Controller.
- In the GCB service, the received HTTP packets are load balanced across the available GCB Pods.
- GCB Pods filters the packets based on the metadata.
- The filtered HTTP packets from GCB Pods are tunneled directly to the Tools or through the GigaVUE V Series nodes on OpenStack environment. Refer to the GigaVUE Cloud Suite for OpenStack Configuration Guide for more information on the GigaVUE V Series configuration on OpenStack environment.
- GCB Controller collects the data from GCB Pods and sends the collected statistics and heartbeats to GigaVUE-FM.